XPS optimizes all work instructions for a given ASC stack. The optimization algorithm evaluates both an idle crane's location and its active work load and decides which job the crane should perform. This decision is based on the following rules:
Avoid crane conflicts: Eliminate, shorten, and split jobs where possible.
Avoid unladen travel: Evaluate the overall schedule and pick the most effective move (not simply the closest one).
Balance service demands: Take into account marine load times and gate wait times.
Based on these rules, you can easily determine why XPS chose one job over another. If you want to influence the decision to achieve an alternative outcome that better fits your unique business demands and operational practices, you can fine-tune order optimization. For example, you can define when a gate wait time should override a marine wait time, at what savings unladen time should win against a service demand, and when XPS should split or shorten a job. For more information, see Setting up block optimization (on page 1) in the online help or on the Kaleris Community Portal.
Order optimization requires the following conditions:
A user has the YRDBMS privilege.
The block associated with the ASC has an optimization dispatcher turned on. For more information, see Manage block automation options (on page 1) in the online help or on the Kaleris Community Portal.
A crane is available, which means that it is online, automated, and idle.
If a crane is online and manual, this means someone is physically controlling it, for example in case of a remote operator handling the direct dispatch to trucks.
For more information, see ASC availability (on page 1).
When optimizing transport orders, XPS performs the following steps:
Starts the optimization engine for the selected ASC block.
Collects all active work instructions into, out of, and within the selected ASC stack.
Eliminates unfeasible work instructions.
The decision to eliminate certain work instructions is based on an ASC's access to transfer zones and the performance of the other ASC in the block. For example, this prevents an ASC from getting a job that is in the way of another ASC's work, keeping the two ASCs in the stack from needing to pass each other.
Determines work instructions that can be split or shortened. This concerns long jobs that are beyond the ASC's range or occur during busy periods. For details, see Split work instructions (on page 1).
Calculates job schedules for the remaining work instructions.
Dispatches the first work instruction in the schedule, which is the one with the lowest score.
This flow differs in the following cases:
The selected ASC is not idle. In this case, XPS waits until the ASC becomes idle.
XPS has eliminated all productive jobs. In this case, AYC Manager finds a pre-position (on page 1) or housekeeping (on page 1) job to dispatch.